HOME

Thatis Micrisoft for you taking
over everything for you.

No58- -Setting Up Your Drive & Some Regular Maintenance suggestions....
We all love our Windows-95 O/S, but it's a fragal system and a memory hog--we still hang right in there. We have all (from time to time) had w-95 get an error on install and (more often) lock-up when the application is performing a task. Well, lend a ear and copy this down to your (I want to keep file).
We have to head off failures, so let's get a good defense. Naturally, you need to back-up as a Doctor friend does, but not a half dozen times a day, but that's another page later. I haven't found any (Uninstallers) that gets ride of everything, I always have to DELETE things and go into the regedit to clean it all out.
I'm going to assume that you didn't partition your drive and that your system was partitioned with windows-95 default set-up. Ok, go to your RUN command and type regedit and click ok, your now in the system registry (so be careful), when you delete here--it's gone, period. Now, click the little plus next to the HKEY_CURRENT_USER, then ck software and look to see if the programs or left over files you thought you deleted is still there. If so, highlight it and hit the delete, next-- ck the + HKEY_LOCAL_MACHINE, then software and do the same, next--ck the + HKEY_USERS, then default, then software and look for some more to delete, when your through--save and exit out.
If you (JUST HAVE TO HAVE) a Un-Installer and don't mind trading a little time for extra peace of mind, you'll find (UnInstaller 4.5 by MicroHelp) the ideal house cleaner for your overstuffed system hard drive.
It upholds the program's long-standing reputation for safety, power, and simplicity. UnInstaller's main focus is safety, its database recognizes crucial Windows system files and prevents you from deleting them. However, it does have a advanced option for the wicked tweeker.
Unlike more aggressive file removers, such as CleanSweep and Remove-It, UnInstaller makes no attempt at all to find unused DLLs, because many so-called "unused" files are in fact used by Windows. For this job, download the Free utility called "Clean System Directory" from:
www.ozemail.com.au/~kevsol/sware.html
I've tested it for 10 months and found it to be safe and very effective in removing those un-wanted "DLL's".

No59- -Keeping It Clean At Boot:
We need to "delete the c:\WINDOWS\TEMP on boot, delete the c:\WINDOWS\RECENT directory at boot, set your browser's cache directory to the TEMP directory, set the TEMP directory to \RECYCLED -- Ok:
This will purge all deleted, temporary and cached files every time the system is Booted. The CHOICE command will ask before deleting the TEMP directory.
Ok, we need to edit "autoexec.bat" OR make one -- Soooo, open it up and add;
"At the very start of the Bat File Type:
set TEMP=c:\recycled
deltree /y c:\windows\recent
deltree /y c:\windows\temp
choice /N /T:Y,5 Remove the contents of the TEMP directory (yn) [Y5] ?
if errorlevel = 2 goto nokilltemp
deltree /y %temp%
md %temp%
:nokilltemp
"Then the rest of the autoexec.bat"

No60- -Recovering From That Crash or LockUp
Windows 95/98 Below Windows 2000 Windows NT 4
WIN 9x:
We'll explain some remidies to try to solve these problems.
Computer Will Not Boot:
This means "at boot" you don't see the message "Starting Windows" or anything. Be sure you download the Ultimate Boot Disk Utility around "Right Here".
(1) Do you see any lights flash "like the floppie" or hear anything "like the hard-drive"?? Is the Power Supply fan moving, swap the power cord with a known good one or check it with an electrical meter. You can also stick a lamp socket in to see if there is power coming from the outlet.
(2) Check ALL the power cables. Is the monitor blank?, see if it has both the data cable and the power cable well attached. We've seen that the "LED" for the monitor could mean either "on" or "stand by". Check the keyboard and mouse cables, are they secure??
(3) Get into your BIOS and do you get BIOS/CMOS error messages or hear any beeps. More info. at our BIOS-CMOS page.
(4) Pop in your boot floppie and at the command prompt, run Scandisk. Then to transfer system files from the floppie to the hard drive type ( A:> sys c: ). Go ahead and run any diagnostic software if you have any.
(5) It's time to open your puters case and check ALL peripheral cables "both to the device and to the motherboard". Double check all your installed cards to see if there secure in there slots.
(6) Still Nothing?? Then try to boot with only your keyboard, mouse, monitor, floppie and video card installed.
(7) You can download this small program (HERE) that can test your CMOS battery (amongst other things) from a dos prompt or goto.
http://www.geocities.com/mbockelkamp/mysoft_d.htm
(8) Still Nothing?? "Unless you have the equipment to check out things like your motherboard" then it's off to your computer repair center.
Next Issue is:
Your Computer goes though the Boot sequence but Windows won't Start:
This means that you can see the message "Starting Windows 95/98" but then you get an error message and get the command prompt (C:\>) or the computer locks up and nothing happens.
Boot your start-up floppie for safe mode command prompt and;
Run Scandisk and fix any problems there then copy the system files from the floppie by typing
(A:> sys c:) "Still nothing??".
Ok, let's check to see if you have some ness. stuff, from the DOS prompt type "set" (without the quotes) and If the files winboot, windir, and temp are there, "If not, we need to add them":
Type
Path = c:\windows
and/or
Path = c:\windows\temp.
Delete temporary files ( under c:\windows\temp and c:\temp ) and delete the swap file so from the same DOS prompt,
type: del c:\windows\win386.swp
If it starts loading but fails with an "Invalid Vxd Error" message, see our DLL pages and the same thing if you get a "Missing Device Driver Error" or a specific error message.
Also if you things half-way decent then start running the W98 troubleshooters at:
Start/ Help/ Contents/ Troubleshooting and use the MS web site Troubleshooters.
OK, the dang thing fires up but still has problems with lockups
Frequent crashes can be caused by "to many reasons to mention here" But a hardware problem like bad RAM memory, crap software, missing or corrupted files, conflicting DLL files, etc. I might mention here and now, 99 times out of 100, start-up problems are caused by improper shut-down issues.
If the computer always boots into safe mode, even when it was shut down properly, the problem can be due to the existence of the file Wnbootng.sts that is created under C:\Windows when errors occurred. So, delete this file if it exists: from the command prompt type del c:\windows\wnbootng.sts
Also, look at the conflict-manager for Hardware Conflict, remove all your Startup Programs so nothing is running in the background (like a AV ie; Norton, etc), and Delete all temp files along with all cache.
Also use the Troubleshooting from; Control Panel/ System/ Performance tab/ File System/ Troubleshooting.
Type "msinfo32" into your RUN command box, pull down the Tool Menu;
RUN "msconfig" and press the advanced button
RUN "sfc" to check all system files
RUN the Automatic Skip Driver
Boot to yout DOS Command and type "scanreg/fix"
If fix doesn't help then Restore the Registry by type; "scanreg/restore" then select a earlier registry date that you know worked

No61- -Windows 2000:
We personally think W2k is the "BEST" operating system to date, but the Stuff To Remember;
(A) You might have to update the MB "BIOS" of some computers to even install W2k.
(B) Take a look at "new hardware" recently added, "driver problems", and "viruses".
(C) If you get "the blue screen of death", write down the message number and look for the explanation at MSKB.
W2k has new recovery procsdures that were not available in NT 4, like starting in safe mode W98 and the recovery console (a command-line console aimed to experienced administrators).
OK (thhat aside), the most common thing that we ran into with beta 3 is that many of the problems are due to non-compliant hardware, so test different devices and MS does publish a list of this officially-compatible products, called Hardware Compatibility List, that is different for every Windows version. On the W2k CD-ROM, it is the file Hcl.txt under the folder Support, or go to:http://www.microsoft.com/hwtest/hcl
I would try booting the computer using "Safe Mode" for the "Last Known Good Configuration".
Next, use the "Recovery Console" to fix a damaged or missing file or from boot disks you can make from it.
Nothing Huh!! Then try the "Emergency Repair Disk" to perform basic repairs, like file system and partition boot sector repairs. So boot the computer using the W2k CD or the boot disks, when prompted, select the Repair option (press R) and choose when prompted the Emergency Repair Option (press R). Then select either the Manual Repair (pressing M) or the Fast Repair (pressing F). The Manual Repair is for experienced users, and the Fast Repair will make an automatic repair.
Lastly, you can run the setup again from the CD.
If It starts but has problems then, use the Event Viewer to get more information about possible problems with a driver. (Start, Settings, Control Panel, Administrative Tools, Event Viewer, System Log) or restore the System to the latest backup.
Last Item To Note:
To create a Emergency Repair Disk, go to the Backup program and select the Welcome tab and click Emergency Repair Disk.
To make the "4" Boot Disks, pop in your W2k CD and look for a "bootdisk" folder and if your CD drive is "D" type
d:\bootdisk\makeboot a:
That's All For Now........

No62- -Windows NT4:
Coming Soon !!!
Tips To Get To Your BIOS and Controling Your Floppie:
CMOS SETUP UTILITY
Your computer has to know how to use a bootdisk. There are 4 things to look for in the BIOS. First, look for Boot Sequence and set it so A or Floppy shows up first in the sequence. Make sure the Boot Up Floppy Seek is ENABLED. Check that the Onboard FDC Controller is ENABLED. Finally, assure that the Onboard FDC Swap A & B is set to No Swap if your 1.44 is at the end of your floppy cable.
How Do I Access My BIOS or CMOS Setup Utility?
A popular way is to hit the Delete key as the computer boots up, but there are many other ways depending on what brand you have, like F10 on Compaqs when the big cursor is in the upper right of the screen for example. Also Ctrl-Alt-Delete, Ctrl-q, Ctrl-s, Alt-s, Esc, Alt-Esc, Alt-Enter, Ctrl-Alt-Esc, Ctrl-Alt-Enter, Ctrl-Alt-F8, and Ctrl-Alt-Insert. Or type setup in DOS on older boxes. Than we have F1, F2, F12, other F keys, Ctrl-Alt-q, Ctrl-Alt-s, Ctrl-Alt-d, Ctrl-Alt-p, Ctrl-Esc, Ctrl-Shift-s and combinations of above.
Here's another list that was posted on usenet that may help.
Sometimes, just holding down a key when you first turn on the computer forces an error which tells you how to enter "setup". Or taking out a set of RAM may cause an adjustment notice where the directions may appear on how to access, or just pulling out the floppy cable or hard drive cable sometimes works.

This looks like the old
Windows. Now when did I
see that before.

No63- -Driver Error's Explained
DRIVER error codes:
Code 1
This device is not configured correctly. (Code 1)
This code means that the system has not had a chance to configure the device. To resolve the problem, follow the instructions in the Device Status box. In addition, you may be able to resolve this issue by removing the device in Device Manager, and then running the Add New Hardware wizard from Control Panel.
Code 2
This code means that the device loader (DevLoader) did not load a device. When this device is a Root Bus DevLoader (for example, ISAPNP, PCI, or BIOS). Windows could not load the driver for this device because the computer is reporting two <type> bus types. (Code 2)
Contact your computer manufacturer to get an updated BIOS for your computer where <type> is ISAPNP, PCI, BIOS, EISA, or ACPI. When the device is not a root bus DevLoader, the following message is displayed
The <type> device loader(s) for this device could not load the device driver. (Code 2) To fix this, click Update Driver to update the device driver where <type> is the DevLoader such as FLOP, ESDI, SCSI, and so on "Update Driver".
In addition to following the recommended solution, try removing the device from Device Manager, and then running the Add New Hardware wizard.
Code 3
The driver for this device may be bad, or your system may be running low on memory or other resources. (Code 3)
To fix this sucker, update the drivers for this device, click Update Driver. To check your computer's memory and system resources, right-click My Computer on your desktop, click Properties, and then click the Performance tab. As an alternative, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 4
This device is not working properly because one of its drivers may be bad, or your registry may be bad. (Code 4)
To fix it, update the drivers for this device, click Update Driver. If that doesn't work, run Scanregw.exe (click Start, click Run, type Scanregw.exe, and then click OK) to check your registry. This code indicates that the .inf file for this device may be incorrect or the registry may be damaged. The error code is displayed if the .inf file specifies a field that should be text, but is binary instead. In addition, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, please contact the hardware's manufacturer for an updated .inf file.
Code 5
The driver for this device requested a resource that Windows does not know how to handle. (Code 5)
To fix this, click Update Driver to update the driver for this device.
This code indicates that there was a device failure due to the lack of an arbitrator. If a device requests a resource type for which there is no arbitrator, you'll receive this error code -- so, update the driver.
Code 6
Another device is using the resources this device needs. (Code 6)
To fix this, shut down your computer, turn it off, and then change the resources for this device. When you have finished, start Device manager and change the resource settings for this device.
This code means that there is a conflict between this device and another device, see the "Troubleshooting Conflicting Hardware" topic in Windows 95 Help, or see the ARTICLE-ID: Q133240 at MS.
Code 7
The message text that is displayed for this error is specific to the driver or enumerator. If the driver does not provide information as to why it failed, the following message is displayed:
The fix for this device is reinstalled driver. (Code 7)
This code means that no configuration can be performed on the device so If the device works correctly, you do need not to perform any steps to correct the code. If the device does not work correctly, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code and the device does not function properly, check with the hardware manufacturer for an updated driver.
Code 8
Several different error messages can be displayed for this error code. This code means that the device loader (DevLoader) for a device could not be found. For example, the .inf file for the device may refer to a missing or invalid file. The error situations are:
A system DevLoader is one that is part of Vmm32.vxd, and typically begins with an asterisk (*). If the DevLoader is a system DevLoader, the following text is displayed "This device is not working properly because Windows cannot load the file <name> that loads the drivers for the device". (Code 8)
The only fix is to run Windows Setup again using your Windows CD where <name> is the system DevLoadert that cannot be found.
If this is not a system DevLoader and the DevLoader cannot be found (the file is missing), the following text is displayed "This device is not working properly because Windows cannot find the file <name> that loads the drivers for the device". (Code 8)
To fix this, click Reinstall Device to reinstall this device where <name> is the DevLoader that is missing.
If this is not a system DevLoader and it can be found on the disk (the file does exist), the following text is displayed: This device is not working properly because the file <name> that loads the drivers for this device is bad. (Code 8)
To fix this, click Update Driver to update the drivers for this device." where <name> is the name of the DevLoader.
If the DevLoader entry is a software key for this device that is missing or an empty string, the following text is displayed:
Device failure: Try changing the driver for this device. If that doesn't work, see your hardware documentation. (Code 8)"
NOTE: For most cases, the resolution is to reinstall or update the driver. As an alternative, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, contact the hardware's manufacturer about updated drivers.
NOTE: When the problem DevLoader is a system DevLoader, Windows should be re-installed because this driver is built into the Vmm32.vxd file.
Code 9
The text for this error code varies, depending on whether or not the device is BIOS/ACPI enumerated. If this is a BIOS or ACPI enumerated device, the following text is displayed: This device is not working properly because the BIOS in your computer is reporting the resources for the device incorrectly. (Code 9)
Da fix, contact your computer manufacturer to get an updated BIOS for your computer.
If this is not a BIOS or ACPI enumerated device (such as an add-in adapter or a device that was plugged in to the computer), the following text is displayed: This device is not working properly because the BIOS in the device is reporting the resources for the device incorrectly. (Code 9)
Again, contact the device manufacturer to get an updated BIOS for your device. This code means that the information in the registry for this device is invalid.
It may be possible to resolve this error by using Device Manager to remove the device and then running the Add New Hardware tool in Control Panel. If you continue to receive this error code, contact the hardware's manufacturer for the proper registry settings or updated drivers.
Code 10
If the device has a "FailReasonString" value in its hardware key, that string is displayed as the error message. The driver or enumerator places this registry string value there. If there is no "FailReasonString" in the hardware key, the following generic error message is displayed: This device is either not present, not working properly, or does not have all the drivers installed. (Code 10)
Try upgrading the device drivers for this device. To resolve this error code, make sure the device is connected to the computer correctly. For example, make sure all cables are plugged in fully and that all adapter cards are properly seated. Follow the suggested solution button and update the device driver. It may be possible to remove the device and redetect it using the Add New Hardware wizard.
Code 11
Windows stopped responding while attempting to start this device, and therefore will never attempt to start this device again. (Code 11)
Da fix,"first" look up ASD in Windows Help and try upgrading the device drivers for this device OR run the Automatic Skip Driver utility from the System Information tool. If the problem persists, contact the hardware manufacturer for updated drivers.
Code 12
This device cannot find any free <type> resources to use. (Code 12)
If you really want to use this device, you must disable another device that is using the resources this device needs. To do this, click Hardware Troubleshooter and follow the instructions in the wizard, where <type> is a resource type (IRQ, DMA, Memory, or I/O).
This code means that one of the resource arbitrators failed. This can occur if the device is software configurable and it does not currently have a resource (if the system is out of resources). For example, all the interrupts are in use, or the device requests a resource that is currently in use by another device that will not release the resource.
To try to fix-it, follow the instructions in the Hardware Troubleshooter. In addition, see the "Troubleshooting Conflicting Hardware" topic in Windows Help, also see ARTICLE-ID: Q133240 at MS.
Code 13
This device is either not present, not working properly, or does not have all the drivers installed. (Code 13)
To have Windows detect whether this device is present or not, click Detect Hardware. This code indicates that the device driver did not find the hardware.
To resolve this error, follow the above. As an alternative, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 14
This device cannot work properly until you restart your computer. (Code 14) You know how to do this---right?
Code 15
This device is causing a resource conflict. (Code 15)
To resolve the conflict, click Hardware Troubleshooter and follow the instructions in the wizard. This code means that the device's resources are conflicting with another device's resources, likely caused by re-enumeration. Also, see the "Troubleshooting Conflicting Hardware" topic in Windows Help, and see ARTICLE-ID: Q133240 at MS.
Code 16
Windows could not identify all the resources this device uses. (Code 16)
To resolve this error code, click the Resources tab in Device Manager to manually enter the settings. Check your hardware documentation to find out what settings to use.
Code 17
The driver information file <name> is telling this child device to use a resource that the parent device does not have or recognize. (Code 17)
To fix this, click Update Driver to update the drivers for this device where <name> is the .inf file for the device. This code means that the hardware is a multiple-function device and the .inf file for the device is providing invalid information on how to split the device's resources to the child devices. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, please contact the hardware's manufacturer about an updated .inf file.
Code 18
The drivers for this device need to be reinstalled. (Code 18)
SOOoooo, reinstall the sucker. If that does not work, try removing the device from Device Manager and then running the Add New Hardware Wizard in Control Panel.
Code 19
Your registry may be bad. (Code 19)
This code means that the registry returned an unknown result so, run Scanreg.exe. If this does not resolve the issue, type "scanreg /restore" (without quotation marks) from a command prompt. Finally, remove the device from Device Manager, and then redetect it using the Add New Hardware tool in Control Panel.
Code 20
Windows could not load one of the drivers for this device. (Code 20)
This code means VxD Loader (Vxdldr) returned an unknown result. For example, there could a version mismatch between the device driver and the operating system. To fix the dang thing, Update Driver. If that does not work, try removing the device from Device Manager and then running the Add New Hardware Wizard in Control Panel.
Code 21
Windows is removing this device. (Code 21)
Close this dialog box, and then wait a few seconds. If this problem continues, restart your computer. This code means that the device has a problem that may be resolved by restarting your computer.
Code 22
The text displayed for this error code differs depending on the circumstances.
If this device is disabled because you disabled it using Device Manager, the following text is displayed:
This device is disabled. (Code 22) So, Click Enable Device to enable this device.
If the device is not started, the following text is displayed:
This device is not started. (Code 22) So, Click Start Device to start this device.
If the device is disabled by a driver or program, the following text is displayed: This device is disabled. (Code 22) You can't enable this device because it has been disabled by a Windows driver. For this sucker, there isn't a fix but the code means that the device is either disabled or has not started. SOoo, try removing the device in Device Manager, then redetecting it using the Add New Hardware wizard. If the problem persists, try a clean boot to rule out software interference. If the error persists, contact the hardware manufacturer.
Code 23
The text displayed for this error code differs depending on the Circumstances. If this device is a secondary display adapter and the primary display adapter was located, the following text is displayed:
This display adapter is functioning correctly. (Code 23)
The problem is with the main display adapter. To view the properties for the main display adapter, so view the Properties.
If this device is a secondary display adapter and the primary display adapter cannot be located, the following text is displayed:
This display adapter is functioning correctly. (Code 23)
The problem is with the main display adapter. Fix the main display adapter, and then this display adapter will work.
If this device is not a display adapter, the following text is displayed: The loaders for this device cannot load the required drivers. (Code 23) So, update the device drivers.
This code means that the device loader delayed the start of a device and then did not inform Windows when it was ready to start the device.
To resolve this error code crap, verify the settings for the primary display adapter in Display properties. Try removing the primary and secondary display adapters from Device Manager, and then rebooting to allow Windows to re-enumerate these devices. Verify that the drivers are current and installed correctly. For devices other than display adapters, follow the recommended solution. If that does not work, try removing the device from Device Manager and using the Add New Hardware wizard to redetect the device.
Code 24
The text displayed for this error code differs depending on the type of device (legacy or Plug and Play).
If this device is a legacy (root detected) device, the following text will be displayed: This device is either not present, not working properly, or does not have all the drivers installed. (Code 24)
To have Windows detect whether this device is present or not, click Detect Hardware. If this is a Plug and Play device, the following text is displayed: This device is either not present, not working properly, or does not have all the drivers installed. (Code 24) Try upgrading the device drivers for this device. This code means that the device was not found (for example, it is missing or is not working properly).
If the device still does not work, make sure the device is connected to your computer correctly. example, make sure all cables are correctly installed, or that the adapter cards are properly seated in their slots.
Code 25
Windows is in the process of setting up this device. (Code 25)
To complete, Restart Computer because this problem typically exists only during the first and second boots after Windows Setup copies all the files. As such, it is likely an incomplete installation. Reinstalling Windows may be required, depending on whether or not the reboot resolves the issue.
Code 26
Windows is in the process of setting up this device. (Code 26)
This code means a device did not load. There may be a problem in the device driver or not all the drivers were installed. Re-install and if this does not work, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, check with the hardware's manufacturer or the Microsoft Software Library for an updated driver.
Code 27
Windows can't specify the resources for this device. (Code 27)
Click the Resources tab, and then select the basic configuration for the resources this device uses. To see which resources this device uses, see the documentation for this device. This code means that the portion of the registry describing possible resources for a device does not contain valid entries. example, the device is marked as configurable, but the configuration information in the .inf file is set to hardwired.
To fix-it, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If the device still does not work, consult the hardware manufacturer for updated drivers or further assistance.
Code 28
The drivers for this device are not installed (Code 28). Heck, Reinstall the Driver. This code means the device was not installed completely.
If that does not work, try removing the device from Device Manager and using the Add New Hardware wizard to redetect it. You may need to obtain updated drivers if the error still occurs.
Code 29
This device is disabled because the BIOS for the device did not give it any resources. (Code 29) You must enable the device in the BIOS. See your hardware documentation for details, or contact your computer manufacturer to get an updated BIOS. This code means that the device has been disabled because the device does not work properly and cannot be made to work properly with Windows. This code may also be present if the device is intentionally disabled in the BIOS.
You may be able to resolve this error code by enabling or disabling the device in the computer's CMOS settings. Windows cannot override this setting. Please contact the computer's manufacturer for assistance with using the computer's CMOS configuration program.
Code 30
This device is using an Interrupt Request (IRQ) resource that is in use by another device and cannot be shared. You must change the conflicting setting or remove the real-mode driver causing the conflict. (Code 30) This code means that an IRQ cannot be shared. This may occur when a PCI/EISA SCSI controller is sharing an IRQ that is also in use by a real-mode device driver that Windows cannot change.
To fix it up, remove the real-mode driver that is using the same IRQ as this device. The real-mode driver may be loading in the Config.sys or Autoexec.bat file.
Code 31 (new in Windows 98)
This device is not working properly because <device> is not working properly. (Code 31) To view the properties for <device> and see why it is not working, click Properties where <device> is the dependent device that must be fixed in order for this device to work properly.
This code appears when a device is dependent on another device to be functioning correctly. This does not include devices that are enumerated by the parent device.
The Properties button displays the properties for the other device. More than likely, the other device will also have one of these Device Manager error codes. Follow all the recommended solutions. If the devices still do not work, remove them from Device Manager and use the Add New Hardware wizard to redetect them. Finally, consult with the hardware manufacturer for updated drivers.
Code 32 (new in Windows 98)
Windows cannot install the drivers for this device because it cannot access the drive or network location that has the setup files on it. (Code 32) To fix this problem, click Restart Computer to restart your computer. If that doesn't work copy all the setup files onto your local hard disk, and run setup from there.
This code indicates that the installation disk or CD-ROM was not available to install the drivers. For example, the CD-ROM drive or network connection is not available. This error typically occurs during the first or second reboot after all the files are copied during Setup, first attempt to restart as suggested. If this does not resolve the problem, determine why the installation disk or CD-ROM is not available. Typically, these devices also have Device Manager codes (such as the CD-ROM controller or network adapter). Resolve the issue to gain access to the installation disk or CD-ROM prior to resolving this conflict.
Code 33 (new in Windows 98)
The message text that is displayed for this error is specific to the driver or enumerator. If the driver does not provide information as to why it did not work, the following message is displayed: This device isn't responding to its driver. (Code 33)
There ian't a fix so contact your hardware vendor. This code typically is displayed when the hardware has failed.

No64- -A few good programs you might want.
On your browser type in www.icq.com there they give you a number after you fill out the form and keep your number and give it to your friends so you can send messages either if you are on or off line. Another one is www.paltalk.com there you can send messages, files and pictures and you can go to a room and tyalk to people in there.

No66- -To Copy, Cut and Paste.
To copy or cut you bring your pointer to the left side and left click and hold it while moving your pointer to the right and down to where you want to copy or cut. Then you can either click on the Ctrl and c- key at the same time for a few. or after to highlight what you want right click and look for copy or cut click on what you want to do. Now to paste go to where you want to paste and bring your pointer to the place and right click on it and left click on paste.

No67- -A free virus scan.
Go to your browser and type in www.grisoft.com and download the virus scan to your my documents and they will send you a number to put in when you finish downloading VIA e-mail in a few. When you get it copy the number down when you can always have it. Then in my documents double click on the virus scan and finish loading it. MAKE SURE YOU SHUT DOWN YOUR OTHER VIRUS SCAN you can't run both. This one they send you a e-mail when you can up date it or you can up date it your-self once a month. Another one is www.esafe.com

No68- -START UP- -RUN COMMANDS USEFUL.
SCANREGW (makes a back up of your registry) - - MSCONF (helps to make config start up programs)- -REGEDIT (lets up edit the registry) (go to find and in name and keep it)- -Hitting the F3 key for more scans of names. Until all complete.- - PING (helps restores with MS-DOS programs. Access DOS Prompt by selecting MS-DOS Prompt from the program category in the start menu. Then simply type ipconfig/all from the DOS prompt. All relevant imfomation will display instantly.

PC- -HELP #5